Skip to content

Add zoom-meeting-manager#236

Closed
uchebuzz-coder wants to merge 2 commits intoopenhome-dev:devfrom
uchebuzz-coder:dev
Closed

Add zoom-meeting-manager#236
uchebuzz-coder wants to merge 2 commits intoopenhome-dev:devfrom
uchebuzz-coder:dev

Conversation

@uchebuzz-coder
Copy link
Copy Markdown
Contributor

@uchebuzz-coder uchebuzz-coder commented Mar 30, 2026

What does this Ability do?

Voice access to your Zoom schedule, meeting details, and cloud recordings. Ask what is next on Zoom, get join links and passcodes, cancel meetings, or (on Pro+) list recordings, summarize transcripts, and play recordings.

Suggested Trigger Words

  • "Zoom meetings"
  • "my Zooms"
  • "Zoom schedule"
  • "today's Zooms"
  • "next Zoom"
  • "Zoom link"
  • "Zoom passcode"
  • "cancel Zoom"
  • "Zoom recording"
  • "summarize Zoom"
  • "Zoom transcript"

Type

  • [0] New community Ability
  • Improvement to existing Ability
  • Bug fix
  • Documentation update

External APIs

  • No external APIs
  • [0] Uses external API(s): Zoom API

Testing

  • [0] Tested in OpenHome Live Editor
  • [0] All exit paths tested (said "stop", "exit", etc.)
  • [0] Error scenarios tested (API down, bad input, etc.)

Checklist

  • [0] Files are in community/my-ability-name/
  • [0] main.py follows SDK pattern (extends MatchingCapability, has register_capability + call)
  • [0] README.md included with description, suggested triggers, and setup
  • [0] resume_normal_flow() called on every exit path
  • [0] No print() — using editor_logging_handler
  • [0] No hardcoded API keys — using placeholders
  • [0] No blocked imports (redis, user_config)
  • [0] No asyncio.sleep() or asyncio.create_task() — using session_tasks
  • [0] Error handling on all external calls
  • [0] Tested in OpenHome Live Editor

Anything else?

@uchebuzz-coder uchebuzz-coder requested a review from a team as a code owner March 30, 2026 20:00
@github-actions
Copy link
Copy Markdown
Contributor

🔀 Branch Merge Check

PR direction: devdev

Failed — Cannot merge 'dev' into 'dev'. Use your feature branch (e.g. slow-music → dev).

Allowed for community contributors:

your-ability-branch  →  dev     ✅

Blocked patterns:

anything             →  main    ❌
dev                 →  dev     ❌
main                →  dev     ❌

Close this PR and re-open it with the correct branch direction.

@github-actions
Copy link
Copy Markdown
Contributor

✅ Community PR Path Check — Passed

All changed files are inside the community/ folder. Looks good!

@github-actions
Copy link
Copy Markdown
Contributor

✅ Ability Validation Passed

📋 Validating: community/zoom-meeting-manager
  ✅ All checks passed!

@github-actions github-actions bot added the community-ability Community-contributed ability label Mar 30, 2026
@github-actions
Copy link
Copy Markdown
Contributor

🔍 Lint Results

🔧 Auto-formatted

Some files were automatically cleaned and formatted with autoflake + autopep8 and committed.

  • Unused imports removed (autoflake)
  • Unused variables removed (autoflake)
  • PEP8 formatting applied (autopep8)

__init__.py Must Be Empty

The following __init__.py files must be completely empty (no code, no comments, no imports):

community/zoom-meeting-manager/__init__.py

__init__.py in ability folders is only used as a package marker. Remove all content from these files.

Files linted: community/zoom-meeting-manager/main.py

✅ Flake8 — Passed

Fix the remaining issues and push again. The lint will re-run automatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

community-ability Community-contributed ability

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant